[ENV] command-service
I. Env Table
| Name | Line | Chain |
|---|---|---|
| NODE_ENV | ||
| MONGO_HOST | ||
| MONGO_URL | ||
| MONGO_REPL | ||
| MONGO_USER | ||
| MONGO_PWD | ||
| USERNAMES | ||
| PASSWORD | ||
| SYNC_NAME | ||
| SYNC_REDIS_HOST | ||
| SYNC_REDIS_PORT | ||
| SYNC_REDIS_PASSWORD |
II. Quick List
Public:
Dev:
https://gitlab.com/gcalls/secrets/gcallsenv/-/blob/master/envLocal/command-service.env
Test:
Prod:
https://gitlab.com/gcalls/secrets/gcallsenv/-/blob/master/envCloud/command-service.env
https://gitlab.com/gcalls/secrets/gcallsenv/-/blob/master/envXR/command-service.env
III. Ticket Table
IV. Flow List
- Check and update new env infomation in Command Service
- Clone Project:
git clone https://gitlab.com/gcalls/secrets/gcallsenv
- Search and note where to use environment variable in Command Service
- Clone Project:
git clone https://gitlab.com/gcalls/publics/gcallsback
- Search and note ticket should change, fix, refactor, research or implement for better env-based productivity development and system performance in Gcalls Issues